This week in Flutter #131: Flutter mad science

6 January 2024

The videos from the Flutter Firebase Festival in Prague are online. I still have to watch them all but I started with Filip’s talk “Flutter Mad Science”, and I was not disappointed. He shows examples of ridiculous things that you can do with Flutter and how they could lead to interesting applications.

- Michele Volpato

🧑‍💻 Development in Flutter

Flutter Multi-Wayed SVG Styling

by Kenneth Michuki

I have recently been involved in a small project that involves handling SVGs as icons in Flutter. One of the issues was that, while we want to possibly apply a color to an icon, applying a color to an SVG is not as straightforward as it might be a multicolored SVG. Kenneth explains the problem and some possible workarounds in this article.

Eliminating ‘Ghost Lines’

by Very Good Ventures

Ghost lines, rendering artifacts that shouldn’t be rendered, was a problem that the Very Good Ventures team encountered while developing Super Dash, a game built with Flutter. The issues are caused by floating-point precision errors. The team explains how they worked around the problem.

🎥 Flutter videos

Creating an AI-Powered Recycling App Using Firebase Extensions

Pavel used Firebase and Firebase Extensions for the back end and Flutter for the client application to create KnowWaste, a socially impactful app, in just 20 days. It uses AI-powered Firebase Extensions, particularly for image labeling and processing photos. The app, which is open source and can be found on Apple Store and Google Play, includes features like scanning waste for recyclability and educational resources.

👨‍💻 Software engineering

The day I started believing in Unit Tests

by Benjamin Richner

“Fast forward about a year. The test ran hundreds if not thousands of times successfully. What a waste of time… But then, one day, we started observing test failures.” Learn how a bug in the test suite helped Benjamin find and fix many bugs in the code.

How to Write Great Tech Specs

by Nicola Ballotta

“… you realized that something was entirely overlooked from the beginning, and now your planned feature will be delayed because it needs to be reworked.”

Nicola explains how to write a good technical specification to avoid this situation.

That’s it for this week.

If you want to comment on any of this week’s entries, you can do it in the comment section below.

Have a bug-free week,